Fix MapInfo parsing for version 0x26#11
Merged
dsjoerg merged 1 commit intoggtracker:upstreamfrom Apr 19, 2016
gravelweb:mini-map
Merged
Fix MapInfo parsing for version 0x26#11dsjoerg merged 1 commit intoggtracker:upstreamfrom gravelweb:mini-map
dsjoerg merged 1 commit intoggtracker:upstreamfrom
gravelweb:mini-map
Conversation
Member
|
how did you figure all this out? how many maps have you tried this on? |
Contributor
Author
|
@dsjoerg I updated dsjoerg/ggtracker#19 with this information. Not sure if I should have included it here instead. Sorry! |
Member
|
its all good 👍 |
Contributor
Author
|
Notice the extra 00 byte in the 3rd line of 1v1 hexdump below 1v1: 2v2: |
Member
|
Parent issue is now ggtracker/ggtrackerstack#7 |
Member
|
Outstanding! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Seems like yet another unknown byte (value=0x00) was added before the camera_* info, so I've added a single read_cstring. I'm not sure if cstring is the right thing here, but how could we possibly know without further information from blizzard, or sample data where this byte is NOT 0x00?